home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
battle31.zip
/
BATTLE.DOC
next >
Wrap
Text File
|
1996-03-09
|
13KB
|
305 lines
┌▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄┐
├▌▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▐┤
────────┤▌ G A M E K E E P E R D O O R W A R E ▐├────────
├▌▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▐┤
├▌▒▒▒▒▒▒▒▒▒ Quality BBS Door Software for Less! ▒▒▒▒▒▒▒▒▐┤
├▌▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▐┤
└▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀┘
B A T T L E F I E L D
~~~~~~~~~~~~~~~~~~~~~
Version 3.0
Copyright (c) Steve Sharpe 1992,1996
SYSTEM REQUIREMENTS
~~~~~~~~~~~~~~~~~~~
1. Any BBS capable of producing one of the following BBS system files:
* DOOR.SYS
* PCBOARD.SYS
* CALLINFO.BBS
* DORINFOx.DEF
2. Battlefield requires ANSI graphics!
SYSTEM OPTIONS
~~~~~~~~~~~~~~
Battlefield supports the use of FOSSIL drivers and non-standard port
addresses. Refer to the INSTALLATION instructions for more information.
FILES CONTAINED IN BATTLE30.ZIP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BATTLE30.EXE <-- The main program
BATTLE.DOC <-- The file you are reading!
GAME.CFG <-- The game configuration file
RESET.EXE <-- Manual game reset program
DATE_CK.EXE <-- Date check file used with registered versions
DOORWARE.DOC <-- Gamekeeper Doorware
FILE_ID.DIZ <-- File description
FILES CREATED BY RESET.EXE
~~~~~~~~~~~~~~~~~~~~~~~~~~
PLAYER1.DAT <-- Player 1 game data **
PLAYER2.DAT <-- Player 2 game data **
FIELD1.DAT <-- Player 1 playing field data **
FIELD2.DAT <-- Player 2 playing field data **
LASTUSER.DAT <-- Indicates last player to play **
RESULTS.DAT <-- Bulletin file for game results [REGISTERED VERSION]
** These files must be present before the door is run (see INSTALLATION).
OVERVIEW
~~~~~~~~
Battlefield is a two-player game where the object of the game is to capture
the opponent's hidden flag. You begin by setting up your playing pieces on
the display grid. Player 1 is red and begins at the top of the grid. Player
2 is light blue and begins at the bottom of the grid. Pieces are placed
anywhere within the first 4 rows on the grid. Flags should be placed where
they can be well protected (by bombs and high value pieces). Player 1 begins
the game. Each player is allowed to move 3 pieces per turn but no piece can
be moved more than once! The lakes in the center of the grid are off-limits
to both players. The game keeps track of captured pieces for both players
during each turn. Most attacks are settled based on the value of each piece
i.e. the player with the highest value (lowest number) wins. To attack the
enemy, players attempt to move one of their pieces to a space occupied by an
enemy piece. The game will determine the outcome. Pieces cannot be moved
diagonally and they cannot jump over other pieces. Bombs and the flag, once
placed, cannot be moved.
PIECE VALUE MOVEMENT COMMENTS
~~~~~ ~~~~~ ~~~~~~~~ ~~~~~~~~
KING.............1....1 SPACE...........WATCH OUT FOR THE ENEMY ROGUE!
KING'S AID.......2....1 SPACE...........NONE
WAR MONGER.......3....1 SPACE...........NONE
FIELD LEADER.....4....1 SPACE...........NONE
SWORDSMAN........5....1 SPACE...........NONE
CANNON KEEPER....6....1 SPACE...........NONE
GUARDSMAN........7....1 SPACE...........NONE
POWDERMAN........8....1 SPACE...........CAN DISARM BOMBS!
MEDIC............9....MULTIPLE SPACES...SACRIFICE TO I.D. DISTANT PIECES!
ROGUE............R....1 SPACE...........CAN KILL A KING!
BOMBS............B....NONE..............NONE
FLAG.............F....NONE..............NONE
Once a player wins, Battlefield automatically resets its data files for a new
game. If the SysOp desires to manually reset the game at anytime, he/she can
run RESET.EXE to reset all data files.
INSTALLATION
~~~~~~~~~~~~
Battlefield is easy to install. Simply follow these steps:
1. 'Unzip' the file BATTLE30.ZIP into the directory of your choice. All
files must remain in the same directory.
2. Run RESET.EXE (type RESET and press ENTER) from the Battlefield directory.
Data files will be created for use by the door.
3. Edit the game configuration file (GAME.CFG) according to the
CONFIGURATION FILE section of these instructions using your favorite word
processor. Ensure you save it as an ASCII text file.
4. Create or edit the batch file your BBS will use to activate the door.
The main door program name is BATTLE30.EXE. For example, if you are running
a Spitfire BBS, you would edit SF.BAT to look similar to the following:
:DOOR_A
REM Place Door A Commands Here
CD\SF\DOORS\BATTLE <-- Change to the Battlefield directory
BATTLE30 GAME.CFG <-- The main program with configuration file argument
CD\SF <-- Change back to the Spitfire directory
GOTO LOOP
NON-STANDARD PORT USE: You may specify the use of non-standard communications
ports with the PORT command. The syntax for the PORT command is PORT:03E8:5,
where 03E8 represents a different base address and 5 indicates the IRQ. For
example, the main program line in the example above would be changed to
BATTLE30 GAME.CFG PORT:03E8:5 to reflect the use of a non-standard comm port.
FOSSIL DRIVER USE: You may specify the use of a FOSSIL driver with the PORT
command added to the main program command line. The syntax for the PORT
command is PORT:F:P, where F instructs the door to use a FOSSIL driver and P
identifies the port. For example, the main program line in the example above
would be changed to BATTLE30 GAME.CFG PORT:F:1 if the SysOp wished to specify
a FOSSIL driver on port 1.
NOTE: The PORT command must be the third command in the main program command
line, if used. If not used, the door defaults to the use of the 4 standard
communications ports (1-4) by reading the BBS file.
Screen Redraw
~~~~~~~~~~~~~
A screen redraw feature is provided. Use this feature if telephone line
noise causes erroneous characters to be displayed.
CONFIGURATION FILE
~~~~~~~~~~~~~~~~~~
Entries in the game configuration file must be accurate or the door cannot be
expected to function properly. Save changes to this file in ASCII text
format. A sample GAME.CFG file is included with the door. This
configuration file can be named any valid DOS filename but the file structure
must be preserved! Edit the door configuration file according to the
instructions below. If you are running a multi-node BBS, simply make 1 copy
of the GAME.CFG file for each node, give each file a unique name, and edit
each file.
Contents of the game configuration file:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Battlefield <-- Line 1 (See below)
c:\sf\door.sys <-- Line 2 " "
The Gamekeeper's Lair <-- Line 3 " "
Steve Sharpe <-- Line 4 " "
000000000000 <-- Line 5 " "
Line 1 - This line reflects the name of the door. The registration algorithm
is based on some of this data. DO NOT CHANGE LINE 1!
Line 2 - Enter the full path and filename for the bbs drop file
applicable to the current node (see SYSTEM REQUIREMENTS).
Line 3 - Enter the name of your BBS.
Line 4 - Enter the SysOp's name.
Line 5 - Enter 12 zeros if the door is not registered. Registered users
enter the registration number provided by the author. Other numbers
will prevent the door from running.
SYSOP KEYS
~~~~~~~~~~
The following keys assist the SysOp in the management of the door:
F5 - Shell to DOS
F8 - Return user to system
F9 - Toggle display on/off
F10 - Chat mode (ESC to exit)
ALT H - Toggle between status lines
[REGISTERED VERSIONS]
The file DATE_CK.EXE (now supplied with the distributed program) can be used
in a BBS event to autom